Updating distributed shards without compromising on consistency

ABSTRACT

In an example embodiment, a first data change and a second data change to data stored in a distributed database are received. The first data change and the second data change are batched in a communication to an index manager. The distributed database is reindexed based on the first data change and the second data change by creating a revised first shard index for a first shard in the distributed database and a revised second shard index for a second shard in the distributed database. The first shard and the second shard are instructed to update respective shard indexes. Confirmation that the first shard index has been updated is received. Then confirmation that the second shard index has been updated is received. In response to both of the confirmations, both the first shard and the second shard are instructed to commit their respective updates.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of U.S. Provisional Application No. 62/101,522, filed Jan. 9, 2015, entitled “UPDATING DISTRIBUTED SHARDS WITHOUT COMPROMISING ON CONSISTENCY,” which is incorporated herein by reference in its entirety.

TECHNICAL FIELD

This document generally relates to methods and systems for use with computer networks. More particularly, this document relates to updating distributed shards without compromising on consistency.

BACKGROUND

The indexing and searching of structured data are important functionalities for many businesses on both sides of sales transactions. For example, sellers may provide access to catalog data (including, for example, product information on various products for sale) to buyers to allow buyers to select items to purchase or contract for. This type of usage is especially prevalent for businesses, which often procure items in large quantities directly from a supplier. Traditionally such structured data was stored in dedicated databases. An authorized buyer, for example, would gain viewing access to a supplier's database and thus be able to search directly the products in the database.

Recently there has been increased movement of data to the cloud. In such cloud environments, there is a lot more data (in both quantity and size) to be stored. This can complicate the process of indexing the data in order for it to be efficiently stored and searched.

BRIEF DESCRIPTION OF DRAWINGS

The present disclosure is illustrated by way of example and not limitation in the following figures.

FIG. 1 is a block diagram illustrating a system, in accordance with an example embodiment, for indexing and searching structured data.

FIG. 2 is a block diagram illustrating a search infrastructure in accordance with an example embodiment.

FIG. 3 is a diagram illustrating an example of elastic assignment of tenants to shards in accordance with an example embodiment.

FIG. 4 is a diagram illustrating an indexer and shard in accordance with an example embodiment.

FIG. 5 is a sequence diagram illustrating a method, in accordance with an example embodiment, for publishing data using the publish protocol.

FIG. 6 is a block diagram illustrating shards in accordance with an example embodiment.

FIG. 7 is a sequence diagram illustrating a method, in accordance with an example embodiment, for updating multiple shards.

FIG. 8 is a flow diagram illustrating a method, in accordance with an example embodiment, for reindexing shards.

FIG. 9 is a block diagram illustrating a mobile device, according to an example embodiment.

FIG. 10 is a block diagram of machine in the example form of a computer system within which instructions may be executed for causing the machine to perform any one or more of the methodologies discussed herein.

DETAILED DESCRIPTION

The description that follows includes illustrative systems, methods, techniques, instruction sequences, and computing machine program products that embody illustrative embodiments. In the following description, for purposes of explanation, numerous specific details are set forth in order to provide an understanding of various embodiments of the inventive subject matter. It will be evident, however, to those skilled in the art, that embodiments of the inventive subject matter may be practiced without these specific details. In general, well-known instruction instances, protocols, structures, and techniques have not been shown in detail.

In an example embodiment, indexing and searching of structured data is provided using an elastic scalable architecture with high availability features. Sharding of data across multiple nodes can be performed dynamically and with elasticity to reduce the possibility of input/output bottlenecks while still being scalable.

FIG. 1 is a block diagram illustrating a system 100, in accordance with an example embodiment, for indexing and searching structured data. The system 100 includes one or more client applications 102A, 102B, 102C, 102D, an index and search manager 104, a distributed database 106, a coordinator 108, and a sharding manager 110. Each client application 102A, 102B, 102C, 102D may represent a different application providing data to be indexed and eventually searched by the system 100. A single tenant (e.g., customer such as a company) may provide multiple clients, while other tenants may provide just a single client. In the depicted figure, client application 102A is or includes a catalog application, client application 102B is or includes an upstream application, client application 102C is or includes a downstream application, and client application 102D is or includes an eStore application.

Client applications 102A, 102B, 102C, 102D may provide one or more of three different types of data streams (not pictured). Each data stream may have its own different data with distinct lifecycle and purpose. These data streams may be known as primary, auxiliary, and relevance and ranking (R/R). The primary data stream may include primary data, which is the data that is the main subject of indexing and searching. The auxiliary data stream may include data that is not directly indexed or searched but may enrich the primary data. The R/R data stream may include R/R data, which is data that plays a role in relevance and ranking of primary data items during searching. As illustrative examples, if the client application 102A provides a catalog, the primary data may include Catalog Interchange Format (CIF) and Catalog Extensible Markup Language (cXML) catalogs, with the auxiliary data including supplier records, type definitions, contracts, and views, and the R/R data including a click stream and transaction data. If the client application 102B provides upstream information, the primary data may include contracts and projects, with the auxiliary data including entitlement information and the R/R data including a click stream. If the client application 102C provides downstream information, the primary data may include approvables, with the auxiliary data including master data and the R/R data including transaction data.

Data streams can be transported as single documents, a multi-part collection, or a set of documents. For each client application 102A, 102B, 102C, 102D, an indexing adapter 112A, 112B, 112C, 112D may be provided. Each indexing adapter 112A, 112B, 112C, 112D can include a parser created to parse document types supported by the corresponding client application 102A, 102B, 102C, 102D. As an example, client application 102A providing catalog data may utilize indexing adapter 112A, which may include a CIF parser (to parse primary CIF catalog data) and various XM parsers for the auxiliary data, such as kit information, Units of Measure (UOM) map, etc. Each parser may have two modes. The first mode can parse the byte stream of the incoming documents into rows. The second mode can parse the rows into an indexable object.

As pictured, the indexing adapters 112A, 112B, 112C, 112D may actually be contained in the index and search manager 104. An index manager 114 may act to manage the indexing process. This may include a queue manager 116 which manages a queue 118 containing incoming data from the client applications 102A, 102B, 102C, 102D, which needs to be indexed. The index manager 114 may act to send data at the front of the queue 118 to the appropriate indexing adapter 112A, 112B, 112C, 112D for the corresponding client while also building a request to an index builder.

In an example embodiment, the index manager 114 may have a redundant architecture that provides an application programming interface (API) to the client applications 102A, 102B, 102C, 102D to allow the client applications 102A, 102B, 102C, 102D to submit indexing jobs. The indexing message produced through the API may contain enough information to uniquely identify the request. This identification could be used to track the status of the submitted jobs.

The index manager 114 may utilize feedback from the distributed database 106 to decide on the indexing jobs to be run in the database 106 to allow a scalable computing architecture for building index shards 120. Specifically, the index manager 114 may send a request to build an index to the index builder 122, which may build the index shards 120. A search core 124 may contain an index updater 126, which can take the index shards 120 and update a local index cache 128 using the index shards 120. This local index cache 128 can then be synchronized with a network file system, which can then distribute the index to the distributed database 106. Each index shard 120 is a subset of the index for a given file type. For example, a shard could include catalog items from a subset of tenants. For large catalogs, a single catalog may span multiple index shards 120.

The distributed database may 106 may contain a data access layer 130, a queue 132, tenant information 134, and documents 136.

The search core 124 may host a Lucene index and answer search queries via search load balancer 138, which acts to balance the load of search requests among multiple instantiations of the search cores 124 on multiple physical or logical servers. The search core 124 may also expose a REST-based search and faceting API (not pictured). The search core 124 may perform aggregation, faceting, ranking, and relevance algorithms on search results. The source documents are primary indexing targets. Each source document may store a document identification key for auxiliary data. In an example embodiment, the auxiliary data itself is stored in the same index shard 120. This allows for locality of reference, so that access to an auxiliary data item related to a primary data item can be easily retrieved during a search.

The search core 124 may keep track of recent changes to the local index cache 128 in a special queue 140 receiving the updates to support search. The updates may be immediately applied to the reader but may be batched before committing to the local index segments.

The index manager 114 may use information from the coordinator 108 and the sharding manager 110 to decide on the indexing jobs to be run in the distributed database 106 to allow a scalable computing architecture for building the index shards 120.

Each index shard 120 may contain Lucene index segments for a set of tenants, as will be described in more detail below. The job of indexing may be designed as a map-reduce job that parses the source document and any auxiliary documents to create the Lucene indexing segments.

Within the local index cache 128, the primary documents may be modeled as Lucene “documents”. The document fields, their indexing properties (stored, indexed, etc.), norms, etc. may be modeled in the bundle providing the local index cache 128. The auxiliary document identifications may be stored in the Lucene document for linking the auxiliary data. The actual auxiliary documents may be stored in the same index as separate documents. For example, a single shard may contain documents relating to a first tenant, including a first catalog item (with item attributes and supplied identification), a second catalog item (with item attributes and supplied identification), a third catalog item (with item attributes and supplied identification), and a supplier document with three different supplier detail files. The supplier document is a single document with the supplier detail files being auxiliary documents. The supplier document may be stored with a key matching the supplier identification field in each source document in the index.

The coordinator 108 may implement a protocol for routing, shard configuration, rolling-apply, and other management functions. The coordinator 108 may additionally provide the node status and consensus protocol.

The sharding manager 110 may implement the elasticity architecture for distributing the index across search cores 124. In an example embodiment, the sharding manager 110 may receive a HyperText Transfer Protocol (HTTP) request for a search and is aware of which search core 124 can respond to this request. It can then route the request to the specific search core 124, perhaps based at least partially on load balancing if multiple search cores 124 can respond to the request. The search core 124 may then use libraries to parse the queries and launch a search and then respond with matches found, in an extensible markup language (XML) document. The XML document may comprise primary data along with the supporting auxiliary data

In an example embodiment, data from the client applications 102A, 102B, 102C, 102D is indexed to be stored in a multi-tenant, multi-modal, distributed database (e.g., distributed database 130). “Multi-tenant” means that the data from one entity is stored along with the data from another entity, which as will be seen makes storage more efficient. “Multi-modal” means that data from multiple client applications 102A, 102B, 102C, 102D of a single entity, including data that is parsed using a completely separate indexing adapter 112A, 112B, 112C, 112D, can be stored within that tenant's area of the distributed database 130. The database 130 itself can then be distributed among multiple physical and/or logical servers.

Additionally, as will be discussed in more detail below, the distribution of the distributed database 130 can be dynamically altered so that tenant can be dynamically reassigned to different physical and/or logical servers at any time. This may be based, for example, on need, which may be based on a combination of factors, including data size, data quantity, size of the entity, and frequency of search.

As described briefly above, sharding allows for the segmentation of large amounts of data to the indexed. A segment may also be known as a tenant and represents a parameter for segmenting data. It can map to a platform tenant or some other type of entity. An object class is a search infrastructure used to support the searching of data items. The object class defines the data. It can indicate that the data is, for example, catalog data, requisition data, contract data, etc.

In an example embodiment, sharding is driven by four goals: availability, scalability, elasticity, and flexibility. Availability indicates that indexed data should be highly available (e.g., little chance of being unable to access the data at any point in time, even if some storage locations are inaccessible or down). Scalability indicates that the search infrastructure should be able to function well as the size grows, both in terms of index size and in terms of search volume. Elasticity indicates that there is an ability to dynamically assign capacity to tenants to make it easier to plan capacity and achieve better resource utilization. Flexibility indicates that different scalability requirements for different tenants or data classes can be supported.

As described above, the indexing itself may be performed using Lucene indexes. Lucene works by taking documents and fields. A document in Lucene is a class that represents a searchable item. The document is converted into a stream of plain-text tokens. The tokens are then analyzed to make the tokens more friendly for indexing and storage. Then the tokens are stored in an inverted index. Additional details about Lucene indexes are beyond the scope of this disclosure.

FIG. 2 is a block diagram illustrating a search infrastructure 200 in accordance with an example embodiment. The search infrastructure 200 includes three layers: an index node layer 202, a name node layer 204, and a load balancer layer 206.

In an example embodiment, the index node layer 202 may comprise a plurality of index nodes 208A-208L, each index node 208A-208L comprising a virtual machine. In addition, each index node 208A-208L can be referred to as a shard. Each shard holds a piece of an index (or sometimes the whole index) for a given tenant. Index nodes 208A-208L are responsible executing searches on the index. It is possible that the entire tenant index fits in a single shard, but the design may assume that the tenant index may need to be distributed across multiple shards. The index manager 210 is responsible for mapping tenants to shards. The mapping information is stored in an index map 212. A federated query (query based on information from multiple sources) may be used if the tenant data is indexed to multiple shards. An index node 208A-208L may look at the tenant-to-shard mapping data stored in the index map 212 to determine if it needs to execute a local search or a federated search.

Elasticity may be accomplished by adding more index nodes 208A-208L as the index size grows or more tenants are added. Additionally, one failed data node should not cause searches to fail. In order to accomplish this, the index manager 210 can replicate the tenant data into two or more shards. In other words, any given index segment for a given tenant can be served by at least two index nodes 208A-208L.

The name node layer 204 may include a plurality of name nodes 214A-214C. Each name node 214A-214C may be an application responsible for mapping a client search request to an index node 208A-208L. Even though any index node 208A-208L may be capable of serving any search request, the goal of the name node 214A-214C is to select an index node 208A-208L that holds at least part of the tenant index. Thus, in the best-case scenario, the local search is executed by the index node 208A-208L that contains the data in its local index.

In an example embodiment, each name node 214A-214C may look at tenant-to-shard mapping data stored in the index map 212. The name node 214A-214C may perform a lookup on the index map 212 and then redirect the search request to the appropriate index node 208A-208L.

The load balancer layer 206 may include a load balancer 216, whose job it is to receive inbound search requests from client APPLICATIONS 218A-218C and invoke one or more name nodes 214A-214C to satisfy the search requests. The load balancer 216 acts to load balance these search requests among the name nodes 214A-214C.

The index manager 210 may be responsible for assigning tenants to shards. This mapping may be dynamic (e.g., the shards may be assigned to the tenants on demand at runtime). Elasticity may be accomplished by dynamically assigning available capacity to tenants on an as-needed basis.

In an example embodiment, the index manager 210 may include a tool used for capacity planning. The goal is to plan enough capacity to support the data needs for all the tenants.

In an example embodiment, the index manager 210 may be implemented by a set of nodes connected to a coordinator in an active-passive type configuration. One of the index manager nodes can be elected as the primary node by the coordinator. The backup index manager nodes can watch the “status” of the primary node and take over if needed. As will be described later, the index manager 210 can be collated with a queue manager. The primary API for the index manager 210 may be based on asynchronous queue based messaging and therefore it makes sense to have the node play a dual role.

In an example embodiment, the index manager node subscribes to one or more tenant queues to receive indexing instructions. This may be the primary interface to the index manager 210. The index manager node may also be connected to the coordinator for watching the current shard configuration information.

Incoming messages may be classified based on the shard configuration, and new indexing tasks that can be created based on the type of messages. Table 1 below describes example structures of these messages:

TABLE 1 Message Schema Description <CIFType> CIF Type definition  CIF File Path for CIF catalog.  DATA position  ENDOFDATA position  Num Items New CIF: CIFType Submits the new Subscription CIF Edited File Path: CIFType indexing task. Tenant ID: String Timestamp: long Subscription Name: String Closure Argument: String New Version CIF: CIFType Creates a new CIF Edited File Path: CIFType version of the Tenant ID: String specified catalog. Timestamp: long The incremental Subscription Name: String loaded version is Closure Argument: String relayed to active Version: int cores using a special NRTUpdate message. Delete Version Tenant ID: String Deletes a Version Timestamp: long Subscription Name: String Closure Argument: String Version: int Delete Tenant ID: String Delete all versions Subscription Timestamp: long for a given Subscription Name: String subscription Closure Argument: String

FIG. 3 is a diagram illustrating an example of elastic assignment of tenants to shards in accordance with an example embodiment. There are three shards 300A, 300B, 300C. The first tenant 302 may be the largest and may be distributed/copied among all three shards 300A, 300B, 300C. The second tenant 304 may be smaller and fit on a single shard, but for high availability purposes is replicated on both shards 300A and 300B. Likewise, third tenant 306 may be smaller and fit on a single shard, but for high availability purposes is replicated on both shards 300A and 300B. Shard 300A and shard 300B may then be fully occupied, whereas shard 300C may have room for more tenants. The assignments depicted here may be dynamically assigned. Thus, for example, if the size of the first tenant 302 shrank significantly while the size of the second tenant 304 grew significantly, the tenants 302, 304 could be redistributed so that the first tenant 302 was only present on shard 300A and shard 300B while the second tenant 304 was present on all three shards 300A, 300B, 300C.

The total capacity of the search infrastructure is proportional to the number of index nodes. The capacity of an index node may be defined in terms of two parameters: index size (the amount of data it can support) and throughput (the number of search results it can handle per second).

The capacity requirement for a tenant may be specified via three variables: index size increment (capacity the tenant will need in a given time window, e.g., number of active catalog items or number of transactions per year), throughput (e.g., number of expected searches per second), and a replication factor (number of times the data has to be replicated to support HA needs, which in the above example is two).

The index map 212 may be the data structure used by the index manager 210 to store tenant-to-shard mappings. The data itself may be stored in the distributed database 130. In an example embodiment, the data structure is defined as described in Table 2.

TABLE 2 Element name Description Usage segment_name It can be tenant name, ANID or any other data segmentation field value. object_class Index manager will index catalog, requisitions, cXML docs, etc. current_shard List of shards containing the Index manager uses current data, it for publishing e.g., shard-1a:shard- tenant data. 3b:shard45c. Index manager This means the current data for should update it a given segment is replicated when a tenant is in shard-1a, shard-3b and assigned a new shard-3c. shard. recent_shards List of shards that contain the Used by data nodes most recent data. to determine the Use some syntax to identify data nodes to replication (e.g., shard- execute the 1a:shard-1b, federated query. shard24d:shard34c). Index manager should update it when a tenant is assigned a new shard. all_shards List of all shards in Data nodes use this chronological order. to execute federated search for older data.

In an example embodiment, each shard holds an index for multiple tenants. For each tenant, the index may include both primary data and auxiliary data. The primary data index can contain auxiliary reference keys.

FIG. 4 is a diagram illustrating an indexer 400 and shard 408 in accordance with an example embodiment. Here, the indexer 400 may store a first tenant index 402. The first tenant index 402 may hold the index source 404 in the distributed database (e.g., the distributed database 130 of FIG. 1). When the indexer 400 receives a publish request, it can copy the index to a temporary local file directory 406, update the first tenant index 402 with data from the request, then copy the first tenant index 402 back to the distributed database. After the whole first tenant index 402 is ready, it can be written to the corresponding shard 408, where it can be stored with a second tenant index 410.

In an example embodiment, each shard represents a final manifestation of a Lucene index ready for searching.

In an example embodiment, full indexing of data can be performed as needed. This is in contrast to previous solutions which could not change the shape of the index.

In an example embodiment, the search component and the indexing component are kept separate, which allows them to run independently and potentially simultaneously. For example, while one tenant is uploading additional data for a catalog to be indexed to the indexing component, another tenant could be searching an existing version of the catalog.

FIG. 5 is a sequence diagram illustrating a method, in accordance with an example embodiment, 500 for publishing data using the publish protocol. The method 500 may utilize a client application 502, a queue manager 504, an index manager 506, a coordinator 508, a document store 510, and a job tracker 512. At operation 514, the client application 502 may send a new upload request to a queue. The location of this queue may be known to the client application 502. The queue may be hosted by the queue manager 504. In an example embodiment, the queue manager 504 may be collocated with the index manager 506. In an example embodiment, the upload request may be formatted as follows:

Message Type: NewFullLoad Tenant: <Tenant name> Subscription: <subscription-name> Version: <version number> Source Document Location: <url to download CIF file> Auxiliary Data Location: <url to download auxiliary data> Closure Argument: <receipt id generated by the application>

The following is an example upload request, written in Extensible Markup Language (XML):

Example xml message: <?xml version=“1.0” encoding=“UTF-8” standalone=“yes”?> <request>  <auxDataURL>http://auxDataURL?param=123</auxDataURL>  <indexAdapterId>catindexer</indexAdapterId>  <initParams>   <entry>    <key>b</key>    <value>2</value>   </entry>   <entry>    <key>c</key>    <value>3</value>   </entry>  </initParams>  <locale>it</locale> <primaryDocumentURL>file://primary%20data</primaryDocument URL>  <publishType>Full</publishType>  <instructions>0</instructions>  <relatedJobld></relatedJobId>  <schemaURL></schemaURL>  <tenantId>p2pTeSg</tenantId> </request>

At operation 516, a procedure is called on the index manager 506 by the queue manager 504. This procedure may, at operation 518, use the information in the upload request to fetch the document to be uploaded (e.g., CIF file if the client application 502 is a catalog application). At operation 520, the index manager 506 asynchronously downloads the document. At operation 522, the index manager 506 validates the document (without parsing). In an example embodiment, the message can be further enhanced to obtain additional information potentially useful for preparing the input split for the indexing Map-Reduce job. The document (with or without the enhanced additional information) can then be stored in the document store 510 at operation 524. The document store 510 may be stored in a distributed database, such as a Hadoop database. At operation 526, the index manager 506 may receive a notification that the document has been saved.

At operation 528, the index manager 506 may query the coordinator 508 to obtain current shard information based on the upload request. This information is used to determine if resharding is necessary or not. At operation 530, the current shard information is sent to the index manager 506 by the coordinator 508.

At operation 532, the index manager 506 then downloads auxiliary data from the client application 502 to enrich the index request even further. At operation 534, the auxiliary data is sent to the index manager 506. At operation 536, the auxiliary data is stored in the document store 510. At operation 538, confirmation of the save is received by the index manager 506.

At operation 540, a request to reindex shards is sent to the job tracker 512. At operation 542, a new index is announced to the coordinator 508. At operation 544, a message is sent from the coordinator 508 to the index manager 506 to update the tracker. Later, the client application 502 may send a check status request to the index manager 506 at operation 546.

In an example embodiment, the distributed database is a Hadoop cluster. The Hadoop cluster is provided to provide a scalable way to build an index, including a full rebuild via Map-Reduce style programming. It also provides a stable storage with replication. In an example embodiment, the Hadoop cluster can be configured with the following configuration:

Name Node 1 HDFS directory Data Nodes 4 HDFS Data Storage Job Tracker 2 Job Controller Task Tracker 4 Running Map-Reduce Tasks Secondary Name Node 1 Backup for HDFS directory

In an example embodiment, for every tenant, shard updates among distributed shards are performed in batches. This allows for updates to be performed without comprising on consistency. Each shard may represent a search index. In order for there to be high availability, multiple copies of the shards may be distributed across multiple virtual or physical devices in a distributed database, either due to replication of the shards or for distribution of the data for a particular tenant among multiple shards. When an update occurs, which may involve rebalancing shards among the devices, multiple updates may be saved and batch updates performed. However, there is still a problem that may occur if consistency isn't ensured.

FIG. 6 is a block diagram illustrating shards in accordance with an example embodiment. Here, tenant 600A has data stored in a first shard 602A and a second shard 602B, while tenant 600B has data stored in the second shard 602B, a third shard 602C, and a fourth shard 602D. Each of the shards 602A-602D may be on their first version, as evidenced by the labels S1-1, S2-1, S3-1, and S4-1. At some point, the tenant 600A may update their data, which may directly cause changes to the first shard 602A and second shard 602B as those shards may contain the data being changed, but may also indirectly cause changes to the third shard 602C and the fourth shard 602D due to rebalancing. These changes may not be performed simultaneously. Specifically, there will always be some lag when communicating between different devices, and the lags may be different for the different devices hosting the distributed database. Thus, even though all four shards 602A, 602B, 602C, and 602D may be changed, these changes may occur at different times, as depicted in FIG. 6.

As can be seen, first the first shard 602A changes from version 1 to version 2 (S1-2), then later the third shard 602C changes from version 1 to version 2 (S3-2), then later the second shard 602B changes from version 1 to version 2, then later the fourth shard 602D changes from version 1 to version 2. The times for these actions may be represented as times T1-T5. A problem is encountered if, for example, a user attempts to perform a search at an intermediate time period, such as time T3. If, for example, the data for the first tenant 600A is replicated between the first shard 602A and the second shard 602B, a different search result will be obtained depending upon whether the search request is fulfilled by the first shard 602A or the second shard 602B, because at time T3 they are on different versions of the index. This can be termed an inconsistency problem.

In an example embodiment, the inconsistency problem is solved by introducing the concept of atomic shard updates where one atomic shard update is defined as comprising n number of indexing jobs and m number of shards to be updated. While the n indexing jobs are performed as they were in FIG. 6, the last part of each indexing job, namely the committing of the updated index to memory (and thus the “activation” of the updated index) is held until all n indexing jobs (up to the point of committing the updates to memory) are complete. For simplicity of wording, an indexing job shall be considered to be completed when a revised index for the corresponding shard has been created, but before the revised index has been committed to the distributed database or the previous version of the revised index overwritten. Once the jobs are all completed, they all can be committed and the shards switched to the new versions simultaneously (or near simultaneously).

FIG. 7 is a sequence diagram illustrating a method 700, in accordance with an example embodiment, for updating multiple shards. In this method 700, the atomic shard update concept described above is combined with a batching mechanism. The method 700 may utilize a queue manager 702, an index manager 704, and a distributed database 706. At operation 708, a first data change is received. This data change may be, for example, a change to primary data or a change to auxiliary data, but could also be a change to one or more factors utilized in distributing data indexes among shards. Namely, the data change may be any change that necessitates a reindexing or rebalancing of indexes. The batch mechanism comes into play here, where instead of immediately reindexing or rebalancing the indexes, the queue manager 702 may store the first data change while it waits to accumulate additional data changes. At operation 710, a second data change is received. It should be noted that while only two data changes are depicted here, the batching mechanism can be designed to accommodate any number of data changes. The frequency at which that the batches can be acted upon can be based on, for example, time (e.g., batches are processed once an hour) or on number of data changes (e.g., batches are processed after every hundred data changes). At operation 712, the first and second data changes are batched and sent to the index manager 704. It should be noted that in an example embodiment the data changes are batched sequentially in a first-in-first-out manner. This means that if the first data change arrived before the second data change, then the batch will put the first data change before the second data change in the list of data changes sent to the index manager 704. This aids in preventing the changes being implemented out-of-order, which could cause additional consistency issues.

At operation 714, the index manager 704 may reindex or rebalance shard indexes based on the batch. In this example, the reindexing or rebalancing may involve four shards in the distributed database 706. At operation 716, the first shard is updated based on the reindexing or rebalancing. At operation 718, the second shard is updated based on the reindexing or rebalancing. At operation 720, the third shard is updated based on the reindexing or rebalancing. At operation 722, the fourth shard is updated based on the reindexing or rebalancing. At operation 724, confirmation that the first shard has been updated is received. At operation 726, confirmation that the second shard has been updated is received. At operation 728, confirmation that the third shard has been updated is received. At operation 730, confirmation that the fourth shard has been updated is received. It should be noted that while operations 716-730 are depicted as occurring in a particular order, in reality the confirmation that a shard has been updated can occur at any time following the update of that shard, and thus operations 716-730 may be comingled or rearranged. Nevertheless, once confirmation that all four shards have been updated, at operation 732 all four shards are instructed to commit their newly revised indexes.

FIG. 8 is a flow diagram illustrating a method 800, in accordance with an example embodiment, for reindexing shards. At operation 802, a first data change is received. At operation 804, a second data change is received. At operation 806, the first data change and the second data change are batched and sent to an index manager for reindexing. At operation 808, a revised first shard index and a revised second shard index are determined based on the first data change and the second data change. At operation 810, the first shard is instructed to update its index based on the revised first shard index. At operation 812, the second shard is instructed to update its index based on the revised second shard index. At operation 814, confirmation that the first shard index has been updated is received. At operation 816, confirmation that the second shard index has been updated is received. At operation 818, in response to the receiving of the confirmations that both the first shard index and the second shard index have been updated, the first shard and the second shard are instructed to commit the revised first shard index and the revised second shard index, respectively.

Example Mobile Device

FIG. 9 is a block diagram illustrating a mobile device 900, according to an example embodiment. The mobile device 900 may include a processor 902. The processor 902 may be any of a variety of different types of commercially available processors 902 suitable for mobile devices 900 (for example, an XScale architecture microprocessor, a microprocessor without interlocked pipeline stages (MIPS) architecture processor, or another type of processor 902). A memory 904, such as a random access memory (RAM), a flash memory, or other type of memory, is typically accessible to the processor 902. The memory 904 may be adapted to store an operating system (OS) 906, as well as application programs 908, such as a mobile location-enabled application that may provide location-based services to a user. The processor 902 may be coupled, either directly or via appropriate intermediary hardware, to a display 910 and to one or more input/output (I/O) devices 912, such as a keypad, a touch panel sensor, a microphone, and the like. Similarly, in some embodiments, the processor 902 may be coupled to a transceiver 914 that interfaces with an antenna 916. The transceiver 914 may be configured to both transmit and receive cellular network signals, wireless data signals, or other types of signals via the antenna 916, depending on the nature of the mobile device 900. Further, in some configurations, a GPS receiver 918 may also make use of the antenna 916 to receive GPS signals.

Modules, Components and Logic

Certain embodiments are described herein as including logic or a number of components, modules, or mechanisms. Modules may constitute either software modules (e.g., code embodied (1) on a non-transitory machine-readable medium or (2) in a transmission signal) or hardware-implemented modules. A hardware-implemented module is a tangible unit capable of performing certain operations and may be configured or arranged in a certain manner. In example embodiments, one or more computer systems (e.g., a standalone, client or server computer system) of one or more processors (e.g., processor 902) may be configured by software (e.g., an application or application portion) as a hardware-implemented module that operates to perform certain operations as described herein.

In various embodiments, a hardware-implemented module may be implemented mechanically or electronically. For example, a hardware-implemented module may comprise dedicated circuitry or logic that is permanently configured (e.g., as a special-purpose processor, such as a field programmable gate array (FPGA) or an application-specific integrated circuit (ASIC)) to perform certain operations. A hardware-implemented module may also comprise programmable logic or circuitry (e.g., as encompassed within a general-purpose processor or other programmable processor) that is temporarily configured by software to perform certain operations. It will be appreciated that the decision to implement a hardware-implemented module mechanically, in dedicated and permanently configured circuitry, or in temporarily configured circuitry (e.g., configured by software) may be driven by cost and time considerations.

Accordingly, the term “hardware-implemented module” should be understood to encompass a tangible entity, be that an entity that is physically constructed, permanently configured (e.g., hardwired) or temporarily or transitorily configured (e.g., programmed) to operate in a certain manner and/or to perform certain operations described herein. Considering embodiments in which hardware-implemented modules are temporarily configured (e.g., programmed), each of the hardware-implemented modules need not be configured or instantiated at any one instance in time. For example, where the hardware-implemented modules comprise a general-purpose processor configured using software, the general-purpose processor may be configured as respective different hardware-implemented modules at different times. Software may accordingly configure a processor, for example, to constitute a particular hardware-implemented module at one instance of time and to constitute a different hardware-implemented module at a different instance of time.

Hardware-implemented modules can provide information to, and receive information from, other hardware-implemented modules. Accordingly, the described hardware-implemented modules may be regarded as being communicatively coupled. Where multiple of such hardware-implemented modules exist contemporaneously, communications may be achieved through signal transmission (e.g., over appropriate circuits and buses that connect the hardware-implemented modules). In embodiments in which multiple hardware-implemented modules are configured or instantiated at different times, communications between such hardware-implemented modules may be achieved, for example, through the storage and retrieval of information in memory structures to which the multiple hardware-implemented modules have access. For example, one hardware-implemented module may perform an operation, and store the output of that operation in a memory device to which it is communicatively coupled. A further hardware-implemented module may then, at a later time, access the memory device to retrieve and process the stored output. Hardware-implemented modules may also initiate communications with input or output devices, and can operate on a resource (e.g., a collection of information).

The various operations of example methods described herein may be performed, at least partially, by one or more processors that are temporarily configured (e.g., by software) or permanently configured to perform the relevant operations. Whether temporarily or permanently configured, such processors may constitute processor-implemented modules that operate to perform one or more operations or functions. The modules referred to herein may, in some example embodiments, comprise processor-implemented modules.

Similarly, the methods described herein may be at least partially processor-implemented. For example, at least some of the operations of a method may be performed by one or more processors or processor-implemented modules. The performance of certain of the operations may be distributed among the one or more processors, not only residing within a single machine, but deployed across a number of machines. In some example embodiments, the processor or processors may be located in a single location (e.g., within a home environment, an office environment or as a server farm), while in other embodiments the processors may be distributed across a number of locations.

The one or more processors may also operate to support performance of the relevant operations in a “cloud computing” environment or as a “software as a service” (SaaS). For example, at least some of the operations may be performed by a group of computers (as examples of machines including processors), these operations being accessible via a network (e.g., the Internet) and via one or more appropriate interfaces (e.g., APIs).

Electronic Apparatus and System

Example embodiments may be implemented in digital electronic circuitry, or in computer hardware, firmware, software, or in combinations of them. Example embodiments may be implemented using a computer program product, e.g., a computer program tangibly embodied in an information carrier, e.g., in a machine-readable medium for execution by, or to control the operation of, data processing apparatus, e.g., a programmable processor, a computer, or multiple computers.

A computer program can be written in any form of programming language, including compiled or interpreted languages, and it can be deployed in any form, including as a stand-alone program or as a module, subroutine, or other unit suitable for use in a computing environment. A computer program can be deployed to be executed on one computer or on multiple computers at one site or distributed across multiple sites and interconnected by a communication network.

In example embodiments, operations may be performed by one or more programmable processors executing a computer program to perform functions by operating on input data and generating output. Method operations can also be performed by, and apparatus of example embodiments may be implemented as, special purpose logic circuitry, e.g., a FPGA or an ASIC.

The computing system can include clients and servers. A client and server are generally remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other. In embodiments deploying a programmable computing system, it will be appreciated that both hardware and software architectures merit consideration. Specifically, it will be appreciated that the choice of whether to implement certain functionality in permanently configured hardware (e.g., an ASIC), in temporarily configured hardware (e.g., a combination of software and a programmable processor), or a combination of permanently and temporarily configured hardware may be a design choice. Below are set out hardware (e.g., machine) and software architectures that may be deployed, in various example embodiments.

Example Machine Architecture and Machine-Readable Medium

FIG. 10 is a block diagram of machine in the example form of a computer system 1000 within which instructions 1024 may be executed for causing the machine to perform any one or more of the methodologies discussed herein. In alternative embodiments, the machine operates as a standalone device or may be connected (e.g., networked) to other machines. In a networked deployment, the machine may operate in the capacity of a server or a client machine in server-client network environment, or as a peer machine in a peer-to-peer (or distributed) network environment. The machine may be a personal computer (PC), a tablet PC, a set-top box (STB), a personal digital assistant (PDA), a cellular telephone, a web appliance, a network router, switch or bridge, or any machine capable of executing instructions (sequential or otherwise) that specify actions to be taken by that machine. Further, while only a single machine is illustrated, the term “machine” shall also be taken to include any collection of machines that individually or jointly execute a set (or multiple sets) of instructions to perform any one or more of the methodologies discussed herein.

The example computer system 1000 includes a processor 1002 (e.g., a central processing unit (CPU), a graphics processing unit (GPU), or both), a main memory 1004, and a static memory 1006, which communicate with each other via a bus 1008. The computer system 1000 may further include a video display unit 1010 (e.g., a liquid crystal display (LCD) or a cathode ray tube (CRT)). The computer system 1000 also includes an alphanumeric input device 1012 (e.g., a keyboard or a touch-sensitive display screen), a user interface (UI) navigation (or cursor control) device 1014 (e.g., a mouse), a disk drive unit 1016, a signal generation device 1018 (e.g., a speaker), and a network interface device 1020.

Machine-Readable Medium

The disk drive unit 1016 includes a machine-readable medium 1022 on which is stored one or more sets of data structures and instructions 1024 (e.g., software) embodying or utilized by any one or more of the methodologies or functions described herein. The instructions 1024 may also reside, completely or at least partially, within the main memory 1004 and/or within the processor 1002 during execution thereof by the computer system 1000, with the main memory 1004 and the processor 1002 also constituting machine-readable media 1022.

While the machine-readable medium 1022 is shown in an example embodiment to be a single medium, the term “machine-readable medium” may include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) that store the one or more instructions 1024 or data structures. The term “machine-readable medium” shall also be taken to include any tangible medium that is capable of storing, encoding or carrying instructions 1024 for execution by the machine and that cause the machine to perform any one or more of the methodologies of the present disclosure or that is capable of storing, encoding or carrying data structures utilized by or associated with such instructions 1024. The term “machine-readable medium” shall accordingly be taken to include, but not be limited to, solid-state memories, and optical and magnetic media. Specific examples of machine-readable media 1022 include non-volatile memory, including by way of example semiconductor memory devices, e.g., erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), and flash memory devices; magnetic disks such as internal hard disks and removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks.

Transmission Medium

The instructions 1024 may further be transmitted or received over a communications network 1026 using a transmission medium. The instructions 1024 may be transmitted using the network interface device 1020 and any one of a number of well-known transfer protocols (e.g., HTTP). Examples of communication networks include a local area network (LAN), a wide area network (WAN), the Internet, mobile telephone networks, plain old telephone (POTS) networks, and wireless data networks (e.g., WiFi and WiMax networks). The term “transmission medium” shall be taken to include any intangible medium that is capable of storing, encoding or carrying instructions 1024 for execution by the machine, and includes digital or analog communications signals or other intangible media to facilitate communication of such software.

Although an embodiment has been described with reference to specific example embodiments, it will be evident that various modifications and changes may be made to these embodiments without departing from the broader spirit and scope of the disclosure. Accordingly, the specification and drawings are to be regarded in an illustrative rather than a restrictive sense. The accompanying drawings that form a part hereof, show by way of illustration, and not of limitation, specific embodiments in which the subject matter may be practiced. The embodiments illustrated are described in sufficient detail to enable those skilled in the art to practice the teachings disclosed herein. Other embodiments may be utilized and derived therefrom, such that structural and logical substitutions and changes may be made without departing from the scope of this disclosure. This Detailed Description, therefore, is not to be taken in a limiting sense, and the scope of various embodiments is defined only by the appended claims, along with the full range of equivalents to which such claims are entitled.

Such embodiments of the inventive subject matter may be referred to herein, individually and/or collectively, by the term “invention” merely for convenience and without intending to voluntarily limit the scope of this application to any single invention or inventive concept if more than one is in fact disclosed. Thus, although specific embodiments have been illustrated and described herein, it should be appreciated that any arrangement calculated to achieve the same purpose may be substituted for the specific embodiments shown. This disclosure is intended to cover any and all adaptations or variations of various embodiments. Combinations of the above embodiments, and other embodiments not specifically described herein, will be apparent to those of skill in the art upon reviewing the above description. 

What is claimed is:
 1. A method comprising: receiving, at a queue manager executed on one or more hardware processors, from a first client application, a first data change to data stored in a distributed database; receiving, at the queue manager, from a second client application different than the first client application, a second data change to the data stored in the distributed database; batching, by the queue manager, the first data change and the second data change in a communication to an index manager; reindexing, by the index manager, the distributed database based on the first data change and the second data change by creating a revised first shard index for a first shard in the distributed database and a revised second shard index for a second shard in the distributed database, wherein the revised first shard index is different than the revised second shard index, wherein the first shard is stored on a first device and the second shard is stored on a second device; instructing, by the index manager, the first shard to update a first shard index based on the revised first shard index; instructing, by the index manager, the second shard to update a second shard index based on the revised second shard index; receiving, at the index manager, at a first time, confirmation, from the first device, that the first shard index has been updated; receiving, at the index manager, at a second time, confirmation, from the second device, that the second shard index has been updated; and in response to both the receiving the confirmation that the first shard index has been updated and the confirmation that the second shard index has been updated, instructing, by the index manager, the first shard to commit the revised first shard index and the second shard to commit the revised second shard index.
 2. The method of claim 1, wherein the first data change is made to primary data.
 3. The method of claim 1, wherein the first data change is made to auxiliary data related to primary data.
 4. The method of claim 1, wherein the first data change is a change to a favor influencing rebalancing of data among the first and second shards.
 5. The method of claim 1, wherein the instructing the first shard to commit the revised first shard index and the second shard to commit the revised second shard index is performed in an order identical to an order in which the first data change and the second data change were received.
 6. The method of claim 1, wherein the reindexing is performed by an index builder in communication with a coordinator.
 7. The method of claim 6, wherein the coordinator maintains shard information.
 8. A system comprising: a distributed database; a search core; and an indexing core executable on one or more processors, the indexing core comprising: a plurality of different index adapters, each index adapter corresponding to a different document type of a different client application; an index builder; an index manager; a queue manager configured to: receive, from a first client application, a first data change to data stored in the distributed database; receive, from a second client application different than the first client application, a second data change to the data stored in the distributed database; and batch the first data change and the second data change in a communication to the index manager; the index manager configured to: cause the index builder to reindex the distributed database based on the first data change and the second data change by creating a revised first shard index for a first shard in the distributed database and a revised second shard index for a second shard in the distributed database, wherein the revised first shard index is different than the revised second shard index, wherein the first shard is stored on a first device and the second shard is stored on a second device; instruct the first shard to update a first shard index based on the revised first shard index; instruct the second shard to update a second shard index based on the revised second shard index; receive, at a first time, from the first device, confirmation that the first shard index has been updated; receive, at a second time, from the second device, confirmation that the second shard index has been updated; and in response to both the receiving the confirmation that the first shard index has been updated and the confirmation that the second shard index has been updated, instruct the first shard to commit the revised first shard index and the second shard to commit the revised second shard index.
 9. The system of claim 8, wherein the first data change is made to primary data.
 10. The system of claim 8, wherein the first data change is made to auxiliary data related to primary data.
 11. The system of claim 8, wherein the first data change is a change to a factor influencing rebalancing of data among the first and second shards.
 12. The system of claim 8, wherein the instructing the first shard to commit the revised first shard index and the second shard to commit the revised second shard index is performed in an order identical to an order in which the first data change and the second data change were received.
 13. The system of claims 8, further comprising a coordinator configured to maintain shard information.
 14. A non-transitory machine-readable storage medium comprising instructions, which when implemented by one or more machines, cause the one or more machines to perform operations comprising: receiving, at a queue manager executed on one or more hardware processors, from a first client application, a first data change to data stored in a distributed database; receiving, at the queue manager, from a second client application different than the first client application, a second data change to the data stored in the distributed database; batching, by the queue manager, the first data change and the second data change in a communication to an index manager; reindexing, by the index manager, the distributed database based on the first data change and the second data change by creating a revised first shard index for a first shard in the distributed database and a revised second shard index for a second shard in the distributed database, wherein the revised first shard index is different than the revised second shard index, wherein the first shard is stored on a first device and the second shard is stored on a second device; instructing, by the index manager, the first shard to update a first shard index based on the revised first shard index; instructing, by the index manager, the second shard to update a second shard index based on the revised second shard index; receiving, at the index manager, at a first time, confirmation, from the first device, that the first shard index has been updated; receiving, at the index manager, at a second time, confirmation, from the second device, that the second shard index has been updated; and in response to both the receiving the confirmation that the first shard index has been updated and the confirmation that the second shard index has been updated, instructing, by the index manager, the first shard to commit the revised first shard index and the second shard to commit the revised second shard index.
 15. The non-transitory machine-readable storage medium of claim 14, wherein the first data change is made to primary data.
 16. The non-transitory machine-readable storage medium of claim 14, wherein the first data change is made to auxiliary data related to primary data.
 17. The non-transitory machine-readable storage medium of claim 14, wherein the first data change is a change to a factor influencing rebalancing of data among the first and second shards.
 18. The non-transitory machine-readable storage medium of claim 14, wherein the instructing the first shard to commit the revised first shard index and the second shard to commit the revised second shard index is performed in an order identical to an order in which the first data change and the second data change were received.
 19. The non-transitory machine-readable storage medium of claim 14, wherein the reindexing is performed by an index builder in communication with a coordinator.
 20. The non-transitory machine-readable storage medium of claim 19, wherein the coordinator maintains shard information. 